I just wanted to copy the readme file, so people can know what it is at first hand.
-------------------------------
IBM DEVICE DRIVER SOURCE KIT VERSION 1.2 FOR OS/2 README (2/94)


INTRODUCTION
============
The IBM Device Driver Source Kit Version 1.2 for OS/2 contains
IBM's latest release of OS/2* source code, build and test tools
for several device drivers and online documentation. These will
be helpful for developing and testing your own device drivers for
OS/2*. This kit is targeted for experienced developers.


This release contains several enhancements over the Version 1.1
release:

o Source code is new or updated with fixes or improvements.

o Several new drivers and tools are included. See "What's New"
and "Components and Build Requirements" in the "Using Your DDK"
online reference.

o Documentation has been expanded and enhanced to explain how to
use the source code. See the "Documentation" section below.

CHANGE/SUPPORT NOTICE
=====================
The source code contained in this DDK, besides sample code,
includes the latest actual, buildable source code that will
produce working drivers for different types of devices. The DDK's
goal is to provide device driver developers with as much of this
tested code as early as possible. However, some of this source
code, such as function calls not documented in the available IBM
Reference Manuals (listed in the "Online Documentation" section,
under "Base Build Structure" in "Using Your DDK"), may be
"preliminary" or "IBM internal use code". This type of code is
considered "unsupported" and is subject to change without notice.


INSTALLING THE DDK
==================
Execute the DDKINST command file contained in the CD-ROM root
directory to start the installation process. The kit installation
program allows installation of selected (or all) components.
Installation DOES NOT UPDATE CONFIG.SYS, regardless of any
installation selection.

INSTALL TOOL NOTES:
-------------------
1) If you are installing over a previous version of the DDK and
you don't want any of your previous DDK files, we supply you
with a tool called "DELDDK", located in the \DDK directory.
This tool will delete all the information (INI information, DDK
folder on desktop and the specified DDK tree) related to the
installed DDK.

WARNING: Make sure to BACKUP any files that you want to save
-------- BEFORE you run DELDDK. ALL files under the DDK tree
will be DELETED by DELDDK.

2) The "Delete the Installed Components and Reinstall" option may
not work in certain situations. To circumvent this problem,
backup any files that you want to save and use the DELDDK tool
to delete the previously installed DDK. You can then run a
fresh install.

3) The "BACKUP" option provided with the Install tool is NOT
supported for this release. Using this option will produce
unpredictable results.


SYSTEM REQUIREMENTS
===================
Disk Space Requirements
-----------------------
As components are selected from the Install - directories panel,
the installation program will display the total hard disk space
(in bytes) necessary to install all of the selected components.
The "Disk space..." button may be selected from the same panel to
review the free space available on each of the drives.

The "bytes needed" figure displayed by the installation program is
an approximation of the MAXIMUM number of bytes of free space,
including Install program work files, that will be required to
perform an installation on a FAT formatted drive. Significantly
less space is required for installation on an HPFS formatted
drive.

The swapper.dat file may grow during installation depending on the
number of components you selected. To do a FULL INSTALL on an 8Mb
RAM machine, at least 15Mb of disk space should be available to
swapper.dat. Machines with more RAM require less disk space
(machines with 16 Mb RAM require at least 10 Mb disk space for a
FULL INSTALL).


Operating System
----------------
To use this kit you need IBM OS/2 2.0 with the OS/2 2.0 Service
Pack (XR06055) or later releases. Use of this kit and its
associated utilities on a system with a release earlier than the
OS/2 2.0 Service Pack may produce unpredictable results.


OS/2 Debug Kernel
-----------------
The OS/2 Debug Kernel is supplied with this DDK, see the
"DOCUMENTATION" and "TOOLS" sections below for more information.
If you plan to use the OS/2 Debug Kernel, then two systems are
required. Designate one system for development and the other,
connected to a COM port, for debugging.


SOFTWARE REQUIREMENTS
=====================
Compilers/Assemblers
--------------------
To determine which particular compiler/assembler is needed for a
specific device driver, refer to the "Using Your DDK" online
reference, under "Components and Build Requirements" or
"Compilers/Assemblers Used".


Microsoft Macro Assembler (MASM)** Version 5.10A.15
---------------------------------------------------
Several drivers require this assembler. It is supplied with this
kit.


Microsoft Macro Assembler (ML)** 6.0
------------------------------------
Some drivers require this assembler. A command file is supplied
in the base directory of the installed kit called COPYASM6.CMD.
This file copies the necessary executables from your installed
copy of Microsoft Macro Assembler 6.0 to the proper directory
under the DDK base directory.


Microsoft C Optimizing Compiler (CL)** Version 6.00A
----------------------------------------------------
Many of the drivers require this compiler. A command file is
supplied in the DDK base directory called COPYC60.CMD. This file
copies the set of needed files from your installed copy of
Microsoft C 6.0 to the proper directories under the DDK base
directory. Some drivers need the following LARGE model libraries
installed: LLIBCMT.LIB, LLIBCDLL.LIB and LLIBCER.LIB
(LLIBCE.LIB). Some drivers need the following SMALL model
libraries installed: SLIBC7P.LIB, SLIBCEP.LIB and SLIBCER.LIB


Microsoft 386 C Compiler (CL386)** Version 6.00.054
---------------------------------------------------
Some drivers require this compiler. It is supplied with the kit.


IBM C Set/2 (ICC)*
------------------
Some drivers require this compiler. A command file is supplied in
the DDK base directory called COPYCSET.CMD. This file copies all
the files from your installed copy of IBM C Set/2* to the proper
directories under the DDK base directory.


IBM Developer's Toolkit for OS/2* 2.1
-------------------------------------
The IBM Developer's Toolkit for OS/2* 2.1, available separately,
is required to build Pen for OS/2* and Multimedia Presentation
Manager/2* drivers.


CAUTION - IBM C Set/2++ *
-------------------------
IBM C Set/2++ * is NOT used in this DDK release. If you have the
IBM C Set/2++ compiler installed on your system, make sure that
you remove any references to its directory in PATH and DPATH
statements of CONFIG.SYS. This is a precautionary step to avoid
any header file discrepancy that might occur between that compiler
and IBM C Set/2, which IS used in this DDK release.


DOCUMENTATION
=============
The BOOK directory, under the DDK base directory, contains the
online documentation. The files contained in this directory are
".INF" files and may be viewed using the OS/2 VIEW command or by
opening the "DDK" folder and selecting the appropriate book,
provided that it was installed.

You may also view the online documentation directly from the
CD-ROM without installing it on your hard drive by using the
supplied DDKREF tool. To do this, type DDKREF from the DDK
directory on the CD-ROM drive. This creates the book icons in a
folder called DDKREF on your desktop. To view a book,
double-click on any desired icon.

Please see the CHANGE/SUPPORT NOTICE near the top of this document
for information on unsupported/undocumented function calls.


OTHER IMPORTANT README DOCUMENTATION
------------------------------------
Valuable documentation that is not available in any other format
can be found as readme files at the component directory level.
Please take the time to find and carefully read these files before
attempting to build the related drivers. Available documentation
in such a format is listed below.


DEVICE DRIVERS
==============
Actual OS/2 device driver source code is provided to help you
develop your OS/2 device drivers. For a complete listing of all
device drivers included in this release, see the "Using Your DDK"
online reference, under "Components and Build Requirements".


TOOLS
=====
Debuggers
---------
OS/2 Debug Kernel
-----------------
The OS/2 Debug Kernel is a low-level debugger that is useful for
device driver debugging. In addition to existing levels of the
OS/2 Debug Kernel, the following new versions of the OS/2 Debug
Kernel are supplied with this DDK:

o Level 6_543 (2.0 Service Pack 2)
o Level 6_617 (2.11 Manufacturing Refresh 1)
o S3, Level 6_599 (Debug kernel for S3 video)

WARNING: The level of the Debug Kernel MUST be an IDENTICAL MATCH
-------- to the level of the OS/2 operating system kernel being
replaced.

The supplied debugger install command, CDINST.CMD will
automatically select one of the supplied levels by
comparing and matching it to the version level of your
installed OS/2.

Manually installing a level of the Debug Kernel which is
not an IDENTICAL MATCH to the level of the installed
operating system will cause your system to function
improperly.

S3/XGA/8514 DISPLAY DRIVERS NOTE
================================
This DDK includes a new, totally integrated video device driver
for S3, 8514, and XGA video accelerator cards. This new driver
provides up to 16.7 million colors and takes advantage of
86C801/86C805 and 86C928 GUI hardware accelerators. The source
code for this new driver is located in \DDK\SRC\PMVIDEO and
supersedes all three drivers mentioned above which HAVE BEEN
DELETED from this release.

A tool is supplied to delete the existing S3, 8514 and XGA trees
in order to avoid any conflict with the new integrated driver.
This tool is called CLEANXGA.CMD, located in the \DDK directory.

WARNING: Make sure to BACKUP any files that you want to save
-------- BEFORE you run CLEANXGA. ALL files under the
specified tree will be DELETED by CLEANXGA.


16-BIT PLOTTER NOTE
===================
All the documentation for 16-bit Plotter has been removed in order
to give way to new 32-bit technology supplied as part of the new
32-bit Plotter driver. Due to the number of requests, we're still
including the SOURCE CODE for the 16-bit Plotter device driver,
but only for this release. This should give developers the
opportunity to analyze the techniques involved in converting these
type of drivers from 16-bit to 32-bit. However, by the next DDK
release, ALL 16-bit Plotter-related source code and documentation
WILL BE REMOVED from the DDK.


TRADEMARKS AND COPYRIGHTS
=========================
The following terms, denoted by an asterisk (*) in this
publication, are trademarks of the IBM Corporation in the United
States and/or other countries:

IBM
IBM C Set/2
IBM C Set/2++
OS/2
Pen for OS/2
Pen for OS/2 Developer's Toolkit
MMPM/2
Multimedia Presentation Manager/2
Multimedia Presentation Manager Toolkit/2
The Developer's Toolkit for OS/2 2.1

The following terms, denoted by a double asterisk (**) in this
publication, are trademarks of other companies:

Adobe and PostScript are trademarks of Adobe Systems Inc.

Microsoft Macro Assembler (MASM), Microsoft Macro Assembler (ML),
Microsoft C Optimizing Compiler (CL), Microsoft 386 C Compiler
(CL386), Windows 3.1 DDK and Windows 3.1 are trademarks of
Microsoft Corp.

Pro AudioSpectrum is a trademark of Media Vision, Inc.

Sound Blaster is a trademark of Creative Technology Ltd.

IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED,
INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND
MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT.
BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED
PATENTS OR COPYRIGHTS.

Copyright IBM Corporation, 1994, all rights reserved.